emain/emain.ts (1)

76-84: Startup log addition looks correct; placeholder/argument counts match.

The new electron=%s placeholder is paired with process.versions.electron, and the total 7 %s specifiers match the 7 arguments. No functional risk.

Optional: consider including Node and Chrome versions for faster triage:

• node=%s via process.versions.node
• chrome=%s via process.versions.chrome

Apply this diff if you want to include them:

-        "waveterm-app starting, data_dir=%s, config_dir=%s electronpath=%s gopath=%s arch=%s/%s electron=%s",
+        "waveterm-app starting, data_dir=%s, config_dir=%s electronpath=%s gopath=%s arch=%s/%s electron=%s node=%s chrome=%s",
         waveDataDir,
         waveConfigDir,
         getElectronAppBasePath(),
         getElectronAppUnpackedBasePath(),
-        unamePlatform,
-        unameArch,
-        process.versions.electron
+        unamePlatform,
+        unameArch,
+        process.versions.electron,
+        process.versions.node,
+        process.versions.chrome

docs/package.json (1)

42-49: ESLint/tooling versions now align to 8.57; verify @types/eslint v9 compatibility.

• Downgrading eslint and @eslint/js to ^8.57.0 is consistent with root; good.
• @types/eslint remains at ^9.x (Line 44, unchanged). This can be fine, but please verify your ESLint config/plugins don’t rely on ESLint 9 APIs.

Also, you added @types/react and @types/react-dom at ^18.3.x while runtime deps are react/react-dom ^18.0.0. Consider aligning runtime to ^18.3.x in docs to avoid subtle type gaps.

If you want to align React versions in docs, update these fields (outside the hunk):

{
  "dependencies": {
    "react": "^18.3.1",
    "react-dom": "^18.3.1"
  }
}

Taskfile.yml (1)

265-268: Include workspaces in npm-check-updates to cover docs and any future packages.

ncu supports scanning workspaces; running it only at the root can miss nested package.json files. Recommend using the workspaces flag.

Apply this diff:

 outdated:
   desc: Check for outdated packages using npm-check-updates.
-  cmd: yarn dlx npm-check-updates
+  cmd: yarn dlx npm-check-updates --workspaces

package.json (1)

65-69: Electron 37 + electron-vite 4 bump: looks good; consider removing @types/electron.

• Upgrading electron to ^37.3.0 and electron-vite to ^4.0.0 is coherent with the main log change and Vite 6. No functional issues spotted here.
• Electron ships its own TypeScript types. Keeping @types/electron (Line 49, unchanged) can cause type drift/conflicts after bumps like this. Consider removing @types/electron unless you have a specific reason to keep it.

If you decide to remove it, also refresh types with a clean install (yarn && ts --project checks).

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.